• User creates XML file conforming with EssenceRegister.xsd that contains details of new key(s)
• User submits this file as part of Registers Submission
• Register Editor:
  • does NOT add this submitted file to the Submission in the Development Area
  • checks entry for required fields and syntax (and corrects if necessary)
  • copies the <Entry> field into the master Essence Element Keys Register XML document at the correct position to maintain the sort order, which is by <UL> field
  • checks against existing entries for duplications
  • ensures that the <Notes> field begins with **PROPOSED**, creating this field if necessary
  • validates the updated document against EssenceRegister.xsd
  • adds a note to the proposal_metadata that this has been done
• Entry remains marked as provisional until Submission is “accepted”, at which point **PROPOSED** is removed from the <Notes> field (or the whole field if this makes it empty) in the master Essence Element Keys Register XML document
  • Note that such edits are made even when the Registers are “closed” (the open/closed mechanism is just to aid with managing the other Registers (which are not manually edited))